perm filename DDMMD.HLP[D,SYS] blob sn#270162 filedate 1977-03-21 generic text, type C, neo UTF8
COMMENT āŠ—   VALID 00002 PAGES
C REC  PAGE   DESCRIPTION
C00001 00001
C00002 00002	Procedure for running memory diagnostics on the KL10
C00005 ENDMK
CāŠ—;
Procedure for running memory diagnostics on the KL10

		Mount tape labelled Console System  Rev 8 on drive 0 and
		tape labelled Memory Diagnostics  Rev 8 on drive 1.
		Press the bootstrap button labelled
DECTAPE
		on the front panel of the KL10.  When the CTY stops typing
		and the tape stops spinning type
KLDCP<CR>
		After the DEC version of KLDCP finishes loading type
P U.RAM<CR>
		to load the DEC version of the microcode (V126).
		After the microcode is loaded, clear core with
MZ 0:1000000<CR>
		if there are 1000000 (octal) words of core (for example).  Type
LT DIAMON$
		To load the DEC diagnostic monitor into the 10's memory and start
		it.  It will ask HELP ?- to which you reply
<CR>
		It will ask you which device you want and you reply
K<CR>
		for KLDCP.  It will procede to load SUBRTN.A10 and KLDDT.A10
		from the currently selected dectape drive.  When it has finished
		this type
↑X
		(to get back to KLDCP; DEC's version doesn't say KLDCP when you do
		this, but you are there just the same) and
DT1<CR>
		to select the other dectape.  Now type (at DIAMON again)
S<CR>
		to tell it to load a single file.  It will ask FILE.EXT to which
		you reply
DDMMD.A10<CR>
		or whatever diagnostic you want it to run.  It will load and start
		it.  When you are all done, you should reload the Stanford version
		of KLDCP and the microcode and do an LD BOOT to get DSKDMP back.